Skip to content

chore(skills): add the rfc-issue skill - #535

Open
filvecchiato wants to merge 1 commit into
mainfrom
chore/rfc-issue-skill
Open

chore(skills): add the rfc-issue skill#535
filvecchiato wants to merge 1 commit into
mainfrom
chore/rfc-issue-skill

Conversation

@filvecchiato

@filvecchiato filvecchiato commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

.claude/skills/rfc-issue/ covers the tracking issue an RFC gets: the title rule (RFC number dropped), the rfc label, and a four-section body — Description, Motivation, Requirements, Tasks — short enough to be read.

It also covers the case where no RFC exists yet, since the issue often precedes the document: the source line names where the idea came from rather than a docs/rfcs/ path for a file nobody wrote.

The rfc skill ends at the document; this one covers the issue on either side of it.

The rfc skill covers the document and stops there, so the tracking issue that
carries an RFC's implementation work had no guidance. This adds it: the title
rule, the four-section body, and what belongs in each section — resulting-state
Description, a Motivation concrete enough to disagree with, Requirements held to
the constraints an implementer cannot get wrong, and a fixed Tasks list keeping
every host box even where a host will not implement.

Covers the case where no RFC PR exists yet too, since the issue often precedes
the document: the source line names where the idea came from rather than a
docs/rfcs/ path for a file nobody wrote, and thin Requirements are the honest
outcome rather than something to pad.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@filvecchiato
filvecchiato requested a review from a team August 28, 2026 06:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants